{"schema_version":"1.7.5","id":"SUSE-SU-2026:1117-1","published":"2026-03-27T11:34:35Z","modified":"2026-05-19T06:28:55.298869258Z","related":["CVE-2025-11468","CVE-2025-12084","CVE-2025-13836","CVE-2025-13837","CVE-2025-15282","CVE-2025-6075","CVE-2026-0672","CVE-2026-0865","CVE-2026-1299","CVE-2026-2297"],"upstream":["CVE-2025-11468","CVE-2025-12084","CVE-2025-13836","CVE-2025-13837","CVE-2025-15282","CVE-2025-6075","CVE-2026-0672","CVE-2026-0865","CVE-2026-1299","CVE-2026-2297"],"summary":"Security update for python311","details":"This update for python311 fixes the following issues:\n\nUpdate to python 3.11.15:\n\n- CVE-2025-6075: quadratic complexity in os.path.expandvars() (bsc#1252974).\n- CVE-2025-11468: header injection with carefully crafted inputs (bsc#1257029).\n- CVE-2025-12084: quadratic complexity in xml.minidom node ID cache clearing (bsc#1254997).\n- CVE-2025-13836: potential memory denial of service in the http.client module (bsc#1254400).\n- CVE-2025-13837: potential memory denial of service in the plistlib module (bsc#1254401).\n- CVE-2025-15282: user-controlled data URLs parsed may allow injecting headers (bsc#1257046).\n- CVE-2026-0672: control characters in http.cookies.Morsel fields and values (bsc#1257031).\n- CVE-2026-0865: C0 control characters within wsgiref.headers.Headers fields, values, and parameters (bsc#1257042).\n- CVE-2026-1299: header injection when an email is serialized due to improper newline quoting (bsc#1257181).\n- CVE-2026-2297: validation bypass via incorrectly handled hook in FileLoader (bsc#1259240).\n\nChangelog:\n\n - gh-144125: BytesGenerator will now refuse to serialize\n (write) headers that are unsafely folded or delimited; see\n verify_generated_headers. (Contributed by Bas Bloemsaat and\n Petr Viktorin in gh-121650) (bsc#1257181, CVE-2026-1299).\n - gh-143935: Fixed a bug in the folding of comments when\n flattening an email message using a modern email policy.\n Comments consisting of a very long sequence of non-foldable\n characters could trigger a forced line wrap that omitted\n the required leading space on the continuation line,\n causing the remainder of the comment to be interpreted as\n a new header field. This enabled header injection with\n carefully crafted inputs (bsc#1257029 CVE-2025-11468).\n - gh-143925: Reject control characters in data: URL media\n types (bsc#1257046, CVE-2025-15282).\n - gh-143919: Reject control characters in http.cookies.Morsel\n fields and values (bsc#1257031, CVE-2026-0672).\n - gh-143916: Reject C0 control characters within\n wsgiref.headers.Headers fields, values, and parameters\n (bsc#1257042, CVE-2026-0865).\n - gh-142145: Remove quadratic behavior in xml.minidom node ID\n cache clearing. In order to do this without breaking\n existing users, we also add the ownerDocument attribute to\n xml.dom.minidom elements and attributes created by directly\n instantiating the Element or Attr class. Note that this way\n of creating nodes is not supported; creator functions like\n xml.dom.Document.documentElement() should be used instead\n (bsc#1254997, CVE-2025-12084).\n - gh-137836: Add support of the 'plaintext' element, RAWTEXT\n elements 'xmp', 'iframe', 'noembed' and 'noframes', and\n optionally RAWTEXT element 'noscript' in\n html.parser.HTMLParser.\n - gh-136063: email.message: ensure linear complexity for\n legacy HTTP parameters parsing. Patch by B�n�dikt Tran.\n - gh-136065: Fix quadratic complexity in\n os.path.expandvars() (bsc#1252974, CVE-2025-6075).\n - gh-119451: Fix a potential memory denial of service in the\n http.client module. When connecting to a malicious server,\n it could cause an arbitrary amount of memory to be\n allocated. This could have led to symptoms including\n a MemoryError, swapping, out of memory (OOM) killed\n processes or containers, or even system crashes\n (CVE-2025-13836, bsc#1254400).\n - gh-119452: Fix a potential memory denial of service in the\n http.server module. When a malicious user is connected to\n the CGI server on Windows, it could cause an arbitrary\n amount of memory to be allocated. This could have led to\n symptoms including a MemoryError, swapping, out of memory\n (OOM) killed processes or containers, or even system\n crashes.\n - gh-119342: Fix a potential memory denial of service in the\n plistlib module. When reading a Plist file received from\n untrusted source, it could cause an arbitrary amount of\n memory to be allocated. This could have led to symptoms\n including a MemoryError, swapping, out of memory (OOM)\n killed processes or containers, or even system crashes\n (bsc#1254401, CVE-2025-13837).\n - Library\n - gh-144833: Fixed a use-after-free in ssl when SSL_new()\n returns NULL in newPySSLSocket(). The error was reported\n via a dangling pointer after the object had already been\n freed.\n - gh-144363: Update bundled libexpat to 2.7.4\n - gh-90949: Add SetAllocTrackerActivationThreshold() and\n SetAllocTrackerMaximumAmplification() to xmlparser objects\n to prevent use of disproportional amounts of dynamic memory\n from within an Expat parser. Patch by B�n�dikt Tran.\n - Core and Builtins\n - gh-120384: Fix an array out of bounds crash in\n list_ass_subscript, which could be invoked via some\n specificly tailored input: including concurrent\n modification of a list object, where one thread assigns\n a slice and another clears it.\n - gh-120298: Fix use-after free in list_richcompare_impl\n which can be invoked via some specificly tailored evil\n input.\n","references":[{"type":"ADVISORY","url":"https://www.suse.com/support/update/announcement/2026/suse-su-20261117-1/"},{"type":"REPORT","url":"https://bugzilla.suse.com/1252974"},{"type":"REPORT","url":"https://bugzilla.suse.com/1254400"},{"type":"REPORT","url":"https://bugzilla.suse.com/1254401"},{"type":"REPORT","url":"https://bugzilla.suse.com/1254997"},{"type":"REPORT","url":"https://bugzilla.suse.com/1257029"},{"type":"REPORT","url":"https://bugzilla.suse.com/1257031"},{"type":"REPORT","url":"https://bugzilla.suse.com/1257042"},{"type":"REPORT","url":"https://bugzilla.suse.com/1257046"},{"type":"REPORT","url":"https://bugzilla.suse.com/1257181"},{"type":"REPORT","url":"https://bugzilla.suse.com/1259240"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2025-11468"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2025-12084"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2025-13836"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2025-13837"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2025-15282"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2025-6075"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-0672"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-0865"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-1299"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2026-2297"}]}